Hybrid automatic repeat request and scheduling for wireless cellular systems with local traffic managers

ABSTRACT

The disclosed subject matter is directed towards scheduling and Hybrid Automatic Repeat Request (HARQ) operations by which nodes in a three party communication system can communicate. To schedule a data transmission from a transmitter node to receiver node(s), a local manager/scheduler node sends common downlink control information to the transmitter and receiver nodes. Via a scheduling request, the transmitting node can request the scheduling of the data transmission by the local manager node. The technology facilitates unicast and broadcast/multicast data transmissions; for a unicast data transmission, the scheduling request identifies the receiving node. The transmitting node can explicitly acknowledge reception of the downlink control information to the local manager node, or the local manager node can detect the data transmission, when it occurs, as an implicit acknowledgment that the common downlink control information was successfully received.

CROSS-REFERENCE TO RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto, U.S. patent application Ser. No. 16/366,254 (now U.S. Pat. No.10,951,362), filed Mar. 27, 2019, and entitled “HYBRID AUTOMATIC REPEATREQUEST AND SCHEDULING FOR WIRELESS CELLULAR SYSTEMS WITH LOCAL TRAFFICMANAGERS,” which application claim further priority to U.S. ProvisionalPatent Application No. 62/717,186, filed on Aug. 10, 2018, and entitled“HYBRID AUTOMATIC REPEAT REQUEST AND SCHEDULING PROCEDURES FOR WIRELESSCELLULAR SYSTEMS WITH LOCAL TRAFFIC MANAGERS,” the entireties of whichapplications are hereby incorporated by reference herein.

TECHNICAL FIELD

The subject application is related to wireless communication systems,and, for example, to fifth generation (5G, sometimes referred to as NewRadio (NR)) cellular wireless communications systems in which localtransmissions are scheduled by a local manager.

BACKGROUND

In traditional wireless cellular communications systems, a givengeographic area is served by a single base station. The range of itstransmitter (the “coverage”) determines the “cell,” which corresponds tothe geographic area in which a user equipment (UE) can be served by thebase station. By arranging a plurality of base stations in such a waythat their coverage areas (the cells), partially overlap, ubiquitouscoverage can be achieved in which user equipment can move through thenetwork and at any given time be served by one base station. When theuser equipment travels towards the edge of one base station's coveragearea and into the coverage area of another base station, mobilityprocedures commonly referred to as “handovers” provide seamlessconnectivity during the time when the user equipment is disconnectingfrom the first base station and connecting to the second base station.

Thus, at any given time, a user equipment is served by a single basestation, whereby control channel and data channel transmissions aretransmitted and received by the same pair of nodes. For example, bothdownlink shared channel and uplink shared channel transmissions arescheduled by a base station, whereby for the downlink transmissions thebase station is the transmitter and the user equipment (UE) is thereceiver, whereas for the uplink transmissions, the UE is thetransmitter and the base station is the receiver.

In next-generation wireless cellular communications systems, newservices, such as vehicular services, are changing this paradigm. Forexample, sidelink technology provides for local (e.g.,vehicle-to-vehicle) traffic to be managed by a local traffic manager,referred to as a “Node-S,” which can perform scheduling between atransmitter node (“Node-T”) and a receiver node (“Node-R”). The sidelinkcomprises an interface between two user equipment, in contrast to thedownlink and uplink interfaces between a base station and a userequipment and a user equipment and a base station, respectively.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless three-party communication systemincluding scheduling nodes, transmitting nodes and receiving nodes thatcan communicate via sidelink transmissions, in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 2 illustrates an example timing diagram showing communicationsbetween a base station and a mobile station device, such as a localmanager device, in accordance with various aspects and embodiments ofthe subject disclosure.

FIG. 3 is an example block diagram representing a local manager device(scheduler node device) scheduling a broadcast/multicast transmissionover sidelink from a transmitter node to receiver nodes, in accordancewith various aspects and embodiments of the subject disclosure.

FIG. 4 is an example block diagram representing a local manager device(scheduler node device) scheduling a unicast transmission over sidelinkfrom a transmitter node to a receiver node, in accordance with variousaspects and embodiments of the subject disclosure.

FIG. 5 is an example block diagram representing a local manager device(scheduler node device) sending downlink control information to atransmitter node, in which the transmitter node acknowledges receipt ofthe downlink control information, in accordance with various aspects andembodiments of the subject disclosure.

FIG. 6 is an example block diagram representing a local manager device(scheduler node device) detecting a transmission from a transmitter nodeto a receiver node, which acts as an implicit acknowledgment of thetransmitter node having received downlink control information from thelocal manager device, in accordance with various aspects and embodimentsof the subject disclosure.

FIG. 7 is an example block diagram representing a transmitter nodesending a scheduling request for transmission of data to a local managerdevice (scheduler node device) so as to obtain downlink controlinformation from the local manager device that schedules thecorresponding data transmission, in accordance with various aspects andembodiments of the subject disclosure.

FIG. 8 illustrates example operations of a local manager node device, inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 9 illustrates example operations of a transmitter node device, inaccordance with various aspects and embodiments of the subjectdisclosure.

FIG. 10 illustrates example operations of a local manager node devicethat receives a scheduling request, in accordance with various aspectsand embodiments of the subject disclosure.

FIG. 11 illustrates an example block diagram of an example mobilehandset operable to engage in a system architecture that facilitateswireless communications according to one or more embodiments describedherein.

FIG. 12 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates wirelesscommunications according to one or more embodiments described herein.

DETAILED DESCRIPTION

Various embodiments of disclosed herein are directed towards schedulingtechnologies and Hybrid Automatic Repeat Request (HARQ) technologiesthat facilitate sidelink communications. In one aspect, a Node-S (e.g.,a scheduler/local manager node) sends common downlink controlinformation (DCI) to a transmitting node (Node-T) and receiving node(s),i.e., one or more Node-R(s). Transmission and reception take place viasidelink interfaces between the user equipment. Note that “downlinkcontrol information” or “DCI” as used herein is not to be construed inany limiting sense. For example, downlink control information or DCI,when used in a Sidelink-related environment, such as with a Node-S, aNode-T and a Node-R, can be alternatively referred to as “SidelinkControl Information” (or “SCI”), e.g., as referred to in RAN1 (RadioAccess Network Layer 1) specification(s). Thus, as used herein, downlinkcontrol information/DCI can be considered interchangeable with SidelinkControl Information/SCI, unless indicated otherwise by the usagecontext.

Described herein is technology that lets a Node-T acknowledge receptionof the downlink control information; (note that in otherstate-of-the-art cellular communications systems, such downlink controlinformation is not acknowledged). Implicit and explicit acknowledgementof reception of the downlink control information by the Node-T aredescribed herein.

Note further that downlink control information and associated data aretransmitted from two different nodes (unlike other state-of-the-artcellular communications systems), namely the downlink controlinformation is transmitted by the Node-S, whereas the data istransmitted by the Node-T. Unicast and broadcast schemes are describedherein.

One or more embodiments are now described with reference to thedrawings, wherein like reference numerals are used to refer to likeelements throughout. In the following description, for purposes ofexplanation, numerous specific details are set forth in order to providea thorough understanding of the various embodiments. It is evident,however, that the various embodiments can be practiced without thesespecific details (and without applying to any particular networkedenvironment or standard).

As used in this disclosure, in some embodiments, the terms “component,”“system” and the like are intended to refer to, or comprise, acomputer-related entity or an entity related to an operational apparatuswith one or more specific functionalities, wherein the entity can beeither hardware, a combination of hardware and software, software, orsoftware in execution. As an example, a component may be, but is notlimited to being, a process running on a processor, a processor, anobject, an executable, a thread of execution, computer-executableinstructions, a program, and/or a computer. By way of illustration andnot limitation, both an application running on a server and the servercan be a component.

One or more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software application orfirmware application executed by a processor, wherein the processor canbe internal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can comprise a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components. While various components have been illustrated asseparate components, it will be appreciated that multiple components canbe implemented as a single component, or a single component can beimplemented as multiple components, without departing from exampleembodiments.

Further, the various embodiments can be implemented as a method,apparatus or article of manufacture using standard programming and/orengineering techniques to produce software, firmware, hardware or anycombination thereof to control a computer to implement the disclosedsubject matter. The term “article of manufacture” as used herein isintended to encompass a computer program accessible from anycomputer-readable (or machine-readable) device or computer-readable (ormachine-readable) storage/communications media. For example, computerreadable storage media can comprise, but are not limited to, magneticstorage devices (e.g., hard disk, floppy disk, magnetic strips), opticaldisks (e.g., compact disk (CD), digital versatile disk (DVD)), smartcards, and flash memory devices (e.g., card, stick, key drive). Ofcourse, those skilled in the art will recognize many modifications canbe made to this configuration without departing from the scope or spiritof the various embodiments.

Moreover, terms such as “mobile device equipment,” “mobile station,”“mobile,” subscriber station,” “access terminal,” “terminal,” “handset,”“communication device,” “mobile device” (and/or terms representingsimilar terminology) can refer to a wireless device utilized by asubscriber or mobile device of a wireless communication service toreceive or convey data, control, voice, video, sound, gaming orsubstantially any data-stream or signaling-stream. The foregoing termsare utilized interchangeably herein and with reference to the relateddrawings. Likewise, the terms “access point (AP),” “Base Station (BS),”BS transceiver, BS device, cell site, cell site device, “gNode B (gNB),”“evolved Node B (eNode B),” “home Node B (HNB)” and the like, areutilized interchangeably in the application, and refer to a wirelessnetwork component or appliance that transmits and/or receives data,control, voice, video, sound, gaming or substantially any data-stream orsignaling-stream from one or more subscriber stations. Data andsignaling streams can be packetized or frame-based flows.

Furthermore, the terms “device,” “communication device,” “mobiledevice,” “subscriber,” “customer entity,” “consumer,” “customer entity,”“entity” and the like are employed interchangeably throughout, unlesscontext warrants particular distinctions among the terms. It should beappreciated that such terms can refer to human entities or automatedcomponents supported through artificial intelligence (e.g., a capacityto make inference based on complex mathematical formalisms), which canprovide simulated vision, sound recognition and so forth.

Embodiments described herein can be exploited in substantially anywireless communication technology, comprising, but not limited to,wireless fidelity (Wi-Fi), global system for mobile communications(GSM), universal mobile telecommunications system (UMTS), worldwideinteroperability for microwave access (WiMAX), enhanced general packetradio service (enhanced GPRS), third generation partnership project(3GPP) long term evolution (LTE), third generation partnership project 2(3GPP2) ultra mobile broadband (UMB), high speed packet access (HSPA),Z-Wave, Zigbee and other 802.XX wireless technologies and/or legacytelecommunication technologies.

As exemplified in FIG. 1, a wireless cellular communications system 100is depicted. A base station 120 provides coverage in geographic area 110comprising the cell. Air interfaces 160, 161, 170 provide downlink anduplink communication links for UEs 140, 141, 150, respectively. Notethat all UEs 140, 141, 150, 151, 152, 153, 154, 155 can be assumed tohave uplink/downlink communication links with base station 120, althoughthis is not expressly depicted in FIG. 1 for purposes of readability.

Air interfaces 180, 181, 182, 183, 184, 185, 190, 191, 192 providesidelink connectivity between two given UEs. A local manager, referredto herein as Node-S, locally controls transmissions on the sidelinkwithin an area (or other grouping) associated with the Node-S. In theexample of FIG. 1, a Node-S 140 controls sidelink transmissions in area101, and a Node-S 141 controls sidelink transmissions in area 131. Ingeneral, a Node-S, such as the Node-S 140, sends common downlink controlinformation (DCI) to a transmitting node (Node-T, such as the node 150)and the receiving node(s), i.e., one or more Node-R(s), such as the node152. Transmission and reception thus occur on the sidelink between UEsof a plurality of UEs.

Described herein is a mechanism that lets the Node-T acknowledgereception of the downlink control information; (note that incontemporary cellular communications systems, downlink controlinformation is not acknowledged). Also, in contrast to contemporarycellular communications systems, the downlink control information andassociated data are transmitted from two different nodes. Moreparticularly, the downlink control information is transmitted by theNode-S 140, whereas data is transmitted by the Node-T 150. Unicast,multicast and broadcast schemes are implemented. Implicit and explicitacknowledgement of the downlink control information by a Node-T aredescribed herein.

In one embodiment, a common downlink control information is sent to thetransmitting (Node-T) and receiving (Node-R) nodes. For example, theNode-S 140 may send downlink control information to the nodes 150, 151,152 via the sidelinks 180, 181, 182, whereby Node-T 150 subsequentlysends data to nodes 151 and 152 via the sidelinks 190, 191. The nodes151 and 152 in this example are each referred to as a Node-R, becausethe Node-T 150 in this example transmits to a plurality of Node-Rs; thisscenario is called the broadcast or multicast scenario. In anotherexample, the Node-S 141 may send downlink control information to thenodes 153, 154 via sidelinks 183,184 whereby the Node-T 153 subsequentlysends data to the Node-R 154 via sidelink 192, e.g., in a unicasttransmission.

Note that in this example, the local manager nodes 140, 141, namely theNode-S 140 and the Node-s 141 in the system 100 are configured to belocal managers by the base station 120 via links 160, 161, whereby anynode can transmit or receive via a sidelink controlled by at least oneNode-S. Hence, whether a node is transmitting (in the Node-T state) orreceiving (in the Node-R state) is dynamically controlled by a Node-S,based on the downlink control information. Note that it is feasible fora Node-S to be elected as a local (group) manager by a group of userequipment nodes without a base station configuration, at leasttemporarily.

Now referring to FIG. 2, a UE 140 may receive a synchronization signal220 from a base station 120. The synchronization signal allows the UE140 to become time and frequency synchronized with base station 120 suchthat UE 140 can receive waveforms carrying information from base station120. The synchronization signal may also convey information needed toreceive the broadcast channel in 221. Amongst other data, informationcarried on the broadcast channel configures the UE to receive a downlinkcontrol channel 222 for scheduling a downlink shared channel 223. Datatransmitted via the downlink shared channel configures the UE toinitiate a random access procedure by transmitting a random accesschannel in 224. The base station schedules a random access response bymeans of a downlink control channel 225 carried on another downlinkshared channel 226. The random access response contains a schedulingassignment and a timing advance for the UE to transmit the first uplinkshared channel transmission in 227. The uplink shared channel conveys auser ID. In case of contention resolution during the random accessprocedure, base station 120 schedules another downlink control channel230 scheduling a downlink shared channel 231 to resolve contention. Yetanother downlink control channel 240 schedules a downlink shared channel241 to initiate configuration of UE 140 for communication with basestation 120. Once UE 140 is fully configured for bi-directional andsecure communication with base station 120 via air interface 160, basestation 120 sends yet another downlink control channel 250 scheduling adownlink shared channel 251 to initiate configuration of UE 140 as aNode-S.

In one or more implementations, base station 120 configures each Node-S140, 141 with orthogonal resource pools. Resources are defined in thetime and frequency domain. For example, in a wireless communicationssystem employing orthogonal frequency-division multiple access (OFDMA)different Node-S may be assigned different subcarrier indices (frequencydomain) and OFDM symbols (time domain) for data transmission. Similarly,the same or different subcarrier indices and OFDM symbols may beconfigured for control channel transmissions. For control channeltransmissions, however, identical time/frequency resources can beconfigured for multiple Node-Ss, whereby each Node-S is assigned adifferent search space for control channel transmissions within theidentical time/frequency resources. Additional resources may beconfigured by base station 120 for each Node-S 140, 141, e.g., forphysical random access channel (PRACH) and physical uplink controlchannel (PUCCH) transmissions. These may be used by a Node-S to sendscheduling requests or other uplink control information (UCI) such aschannel state information (CSI) feedback or HARQ acknowledgements.

Similarly, the base station 120 configures UEs 150, 151, 152, 153, 154,155 for communication via sidelinks. Unlike Node-S UEs, which areconfigured by base station 120 as a Node-S via dedicated signaling (e.g.to configure the orthogonal resource pools and search spaces), UEs thattransmit and receive via a sidelink but are not configured as a localmanager/Node-S—that is, these nodes are controlled by a Node-S ratherthan being configured as one—can be configured for sidelinkcommunication under the control of a local manager via common signaling.In particular, a given node that is not a Node-S is aware of theresource pools of the Node-S within cell 110. In one embodiment, thesenodes are configured by common broadcast signaling from the base station120, however, configuration by dedicated messages is not precluded. Forexample, sidelink information including the resource pools of all Node-Sin 110 can be included as part of the radio resource control (RRC) setupor reconfiguration of a node 150, 151, 152, 153, 154, 155. Because agiven node that is not a Node-S is aware of the resource pools of theone or more Node-S in 110, such a node can receive downlink controlinformation from one or more Node-S in its proximity. This isillustrated in FIG. 1 for UE 151, which can receive from a first Node-S140 via a first sidelink 181 and from a second Node-S 141 via a secondsidelink 185, respectively.

As mentioned herein, the nodes 150, 151, 152, 153, 154, 155 areconfigured to receive from the Node-S 140, 141 by base station 120.Hence, when monitoring for downlink control information, a given node150, 151, 152, 153, 154, 155 potentially can receive downlink controlinformation from multiple Node-Ss. This allows for a seamless transitionbetween a local area 130 controlled by a first local manager Node-S 140and a local area 131 controlled by a second local manager Node-S 141. Inparticular, such a transition does not require a handover or any othersignaling from base station 120.

Described herein is facilitating data transmission via the sidelinks ina wireless communications system 100, whereby the communication via thesidelink is controlled by local traffic managers Node-S 140, 141. Notethat in traditional state-of-the-art communications systems, controlchannel and data channel transmissions are transmitted and received bythe same pair of nodes. For example, in FIG. 2, both downlink sharedchannel and uplink shared channel transmissions are scheduled by basestation 120, whereby for the downlink base station 120 is thetransmitter and UE 140 is the receiver, and whereby for the uplink, UE140 is the transmitter and base station 120 is the receiver. Even forthe state-of-the-art sidelink, e.g., in the device-to-device (D2D)feature of the Long-Term Evolution (LTE) standard defined by the ThirdGeneration Partnership Project (3GPPP), the control and datatransmissions occur between two UEs. In the embodiments describedherein, and unlike prior art that exclusively deals with pairs of nodes,a three-party communication sidelink design is provided. The HARQ andscheduling procedures of a three-party communication sidelink design aredescribed herein.

Unlike traditional D2D or vehicle-to-vehicle (V2V) communicationssystems, which deal with pairs of nodes, in which for a given node thesidelink control channel and the sidelink data channel transmissionsoccur between the same pair of nodes, in one or more embodimentsdescribed herein, downlink control information is transmitted by aNode-S and data is transmitted by a Node-T and received by a Node-R.Generally, Node-S, Node-T, and Node-R are three distinct nodes, however,a scenario in which a Node-S also acts as a transmitter Node-T are notprecluded. Furthermore, as discussed herein, whether a node acts astransmitter (Node-T) or receiver (node-R) is generally controlled by theNode-S, depending on whether the downlink control information sent byNode-S and received by a given node instructs the receiving node totransmit (in which case it acts as Node-T) or to receive (in which caseit acts as Node-R).

For example, as generally represented in FIG. 3, the Node-S 140 sendsdownlink control information (via sidelinks 180, 181, 182, FIG. 1) tothe nodes 150 and 152 (as well as the node 151, not shown in FIG. 3).The downlink control information instructs the node 150 to act as atransmitting Node-T and instructs nodes 151, 152 to act as receiverNode-R nodes. This dynamic instruction subsequently allows the Node-T150 to broadcast/multicast data to the nodes 151, 152 (via sidelinks190, 191, FIG. 1).

Similarly, as represented in FIG. 4, the Node-S 141 can send downlinkcontrol information via sidelinks 183, 184 to nodes 153 and 154,instructing node 153 to act as Node-T and instructing nodes 154 to actas Node-R. This dynamic instruction subsequently allows Node-T 153 tosend data to node 154 via sidelink 192 (FIG. 1). In this scenario, thedata transmission between the nodes 153 and 154 is referred to asunicast, i.e., between a transmitter and receiver pair of UEs, unlike inthe previous example of FIG. 3 where one UE (the Node-T) sends data to aplurality of receiver UEs (Node-R).

The downlink control information is generally transmitted on a downlinkcontrol channel, e.g., the physical downlink control channel (PDCCH) inthe 3GPP LTE standard. Unicast and multicast/broadcast transmissions ofdownlink control information are realized by different radio networktemporary identifiers (RNTIs). Returning to FIG. 2, downlink sharedchannel transmission 223 is a broadcast transmission. In 3GPP LTE, thistransmission carries system information (SI) such as the SystemInformation Block 1 (SIB1) and the System Information Block 2 (SIB2). Inthis example, the downlink shared channel 223 is scheduled by a PDCCH222 whose cyclic redundancy check (CRC) bits are scrambled with theSI-RNTI. The downlink shared channel transmission 241, on the otherhand, is a unicast transmission. In 3GPP LTE, this transmission isscheduled by a PDCCH 240 whose cyclic redundancy check (CRC) bits arescrambled with the C-RNTI. The C-RNTI is unique to the UEs in cell 110(FIG. 1) and is configured by base station 120 via dedicated RRCsignaling. Because only the base station 120 can send downlinktransmissions, in prior systems it suffices to indicate a receiver inthe downlink control information. For unicast transmissions, this isdone by the C-RNTI, which indicates for which UE in cell 110 a givenPDCCH is intended. For multicast/broadcast transmissions, a common RNTIis used. Hence, the PDCCH is still send by a dedicated node, the basestation 120, and the common RNTI indicates a plurality of UEs asreceivers. Nevertheless, in each case the downlink controlinformation/RNTI only informs the UE about the intended receiver.

For three-party communications systems as described herein, downlinkcontrol information is described that indicates both the transmittingand the receiving nodes. In other words, as generally represented inFIGS. 3 and 4, the same downlink control information is received by thetransmitter (Node-T) 150 and the receiver or receivers (Node-R) 151 and152 (FIG. 3) or 154 (FIG. 4). Note that in contrast, in the uplink ordownlink scenario or in the existing D2D sidelink, the downlink controlinformation only signals which node transmits (e.g., uplink) or receives(e.g., downlink), whereas the other node (the receiving node in theuplink and the transmitting node in the downlink) is implicit.

Thus, in one or more embodiments described herein, a common RNTI (radionetwork temporary identifiers) is defined for sidelink transmissions. Inone example, the one or more Node-S(s) in the cell 110 share the sameRNTI. This is possible if resource pools are strictly orthogonal.Alternatively, each Node-S may be configured with its own RNTI.Moreover, the downlink control information transmitted by a Node-S maycontain a Tx-UID (transmitting node unique identifier) field and anRx-UID (receiving node unique identifier) field, whereby the Tx-UIDfield determines the transmitting node and the Rx-UID field informs thereceiving node(s). For the broadcast/multicast scenario, only a Tx-UIDfield may be part of the downlink control information, whereas the groupof receivers may be determined based on the RNTI and/or the resourcepool associated with the control channel transmission carrying thedownlink control information. For example, a node may detect a downlinkcontrol information transmission by a Node-S with the Tx-UID field setto a value corresponding to another node. Hence, that node knows it isin receiving mode (Node-R).

For the unicast scenario, transmission parameters for the downlinkcontrol information may be uniquely configured for a pair of UEs. TheTx-UID and Rx-UID field are also uniquely assigned to each UE. Forinstance, the Tx-UID field may be assigned to a first UE and the Rx-UIDfield may be assigned to a second UE. A first value, e.g., zero, mayindicate to transmit and a second value, e.g., one, may indicate toreceive. Then {0,1} signals the first UE to transmit and signals thesecond UE to receive.

In this way, there is facilitated a scheduling procedure for three-partycommunication systems. Further described herein is how a HARQ procedurecan be implemented. Note that in prior systems, HARQ is only defined fordata transmissions. For example, a UE 140 may receive a PDCCH 240 and,subsequently, the associated PDSCH 241. However, the UE can fail tosuccessfully decode the data carried on the PDSCH 241, and thus canindicate on a PUCCH to the base station 120 that reception of PDSCH 241was unsuccessful. This triggers another PDCCH and associated PDSCH witha retransmission. In the event the UE 140 did not decode the PDCCHsuccessfully, the UE 140 will not send a PUCCH indicating adiscontinuous transmission (DTX) event to the base station, thereby alsotriggering a retransmission of the PDCCH and PDSCH.

In contrast, for three-party communications systems, the downlinkcontrol information is sent by the Node-S and the subsequent datatransmission is sent by the Node-T. Hence, the scheduling Node-S needsto be informed about discontinuous transmission events at the Node-T,i.e., the scenario in which a Node-T did not successfully receive thedownlink control information from the Node-S.

In one or more embodiments described herein, the Node-T sends anexplicit acknowledgment to the Node-S as to whether the downlink controlinformation (circled label 1 in FIG. 5) from Node-S was receivedsuccessfully. If received successfully, the Node-S deems the downlinkcontrol information as having been successfully received (and the datatransmission sent), and can thus continue other local manager and userequipment operations. If not received successfully, the Node-Sretransmits corresponding downlink control information, e.g.,identifying the same transmitter node-T and updating the scheduling(e.g. time slots) as appropriate. The detailed procedure can utilize oneor more features of state-of-the-art systems, i.e., the downlink controlinformation can indicate the resources for the transmission from Node-Tto Node-S indicating whether the downlink control information wassuccessfully decoded or not. Note that the solid line in FIG. 5 (circledlabel 2) represents such an explicit acknowledgement.

In one or more alternative embodiments, the indication can be implicit.For example, as in FIG. 3 or 4, the Node-S may try to receive the datatransmission from Node-T to Node-R scheduled by the downlink controlinformation sent from Node-S to Node-T and Node-R. If Node-S can detectthe data transmission, as in FIG. 6, the Node-S knows implicitly thatNode-T received the downlink control information successfully, and candeem the sending of the downlink control information as successfullycompleted. Note that if not detected, then the Node-S can reschedule thedata transmission via updated downlink control information; in the eventthat the Node-T had indeed successfully received the previous downlinkcontrol information and transmitted the data transmission, but theNode-S did not successfully detect the data transmission, the Node-T canexplicitly indicate to the Node-S that the previous downlink controlinformation was received and the data transmission was already sent.

Further, procedures are described herein that allow a Node-T to indicateto a Node-S that the Node-T has data to transmit via the sidelink to oneor more Node-R(s). In one or more embodiments, periodic resources forscheduling requests (SRs) are configured by each Node-S, during which aNode-T can transmit to the Node-S (FIG. 7, arrow labeled one (1)) toindicate Node-T has data to transmit on the sidelink to one or moreNode-R. Unlike prior systems, because the Node-S sends its downlinkcontrol information (arrow labeled two (2)) to both the Node-T and theNode-R (with three-party communications systems as described herein),the scheduling request needs to indicate the transmitting node and thereceiving node(s). For multicast/broadcast, it may suffice to indicatethe transmitting node in the scheduling request, as there is no singleintended receiver. For unicast transmissions on the sidelink of athree-party communications system, however, the scheduling request needsto indicate both the transmitting node (Node-T) and the receiving node(Node-R).

The transmitting node is thus the node transmitting the schedulingrequest to the Node-S. For unicast transmissions on the sidelink, it isbeneficial for the Node-T sending the scheduling request to know whethera given intended Node-R is under the control of a given Node-S. In oneor more embodiments, the Node-S broadcasts the set of nodes under itscontrol, e.g., periodically or on demand. Subsequently, when the Node-Tsends the scheduling request in addition to its own identifier, theNode-T can include the identifier of the intended receiver (Node-R) inthe scheduling request. The scheduling request can be received either bya single Node-S or by a plurality of Node-S's depending on how the basestation 120 configures the Node-S's 140, 141 (via the links 160, 161)with scheduling request resources. In the event that a schedulingrequest transmission can be received by a plurality of Node-S's, the setof potential Node-R(s) for unicast transmissions can be broadcast by thebase station 120 rather than by a Node-S.

As can be seen, the technology described herein facilitates datacommunication in a three-party wireless communication system having ascheduling node, transmitting node and receiving node(s). The technologyincludes common DCI broadcasts/multicasts, an explicit or implicitacknowledgement subsystem, and scheduling request operations.

One or more aspects, such as those implemented in example operations(e.g., performed by local manager node device comprising a processor) ofa method, are represented in FIG. 8, and are directed towardsconfiguring (operation 802) common downlink control information thatidentifies a transmitter node device managed by the local manager nodedevice and schedules an associated data transmission by the transmitternode device to a receiver node device in a three-party wirelesscommunication system. Operation 804 represents transmitting the commondownlink control information to the transmitter node device and thereceiver node device. Operation 806 represents, in response todetermining that the common downlink control information was correctlyreceived by the transmitter node device, deeming the transmitting of thecommon downlink control information as successfully completed. Operation808 represents, in response to determining that the common downlinkcontrol information was not correctly received by the transmitter nodedevice, retransmitting corresponding common downlink control informationto the transmitter node device and the receiver node device, in whichthe corresponding common downlink control information identifies thetransmitter node device and reschedules an associated data transmissionby the transmitter node device to the receiver node device.

Aspects can comprise, receiving, by the local manager, an explicitacknowledgment from the transmitting device indicating that the commondownlink control information was successfully received by thetransmitting device, and wherein the determining that the commondownlink control information was correctly received by the transmitternode device is based on the explicit acknowledgment.

Aspects can comprise detecting, by the local manager, a datatransmission from the transmitter node device that corresponds to thecommon downlink control information, and using the detecting as animplicit acknowledgment that the common downlink control information wascorrectly received by the transmitter node device, wherein thedetermining that the common downlink control information was correctlyreceived by the transmitter node device is based on the implicitacknowledgment.

Configuring the common downlink control information can comprise addinga transmitter unique identifier that represents the transmitter nodedevice to a transmitter unique identifier field in the common downlinkcontrol information.

The data transmission can comprise a unicast data transmission, andwherein the configuring the common downlink control information cancomprise identifying the receiver node device in the common downlinkcontrol information.

Configuring the common downlink control information can comprise addinga transmitter unique identifier that represents the transmitter nodedevice to a transmitter unique identifier field and adding a receiverunique identifier that represents the receiver node device to a receiverunique identifier field in the common downlink control information.

Aspects can comprise receiving, by the local manager node device, ascheduling request from the transmitter node device, and configuring thecommon downlink control information and the transmitting the commondownlink control information can occur in response to the schedulingrequest.

The local manager node device can comprise a first local manager nodedevice in a cell; aspects can comprise receiving, by the local managernode device from a base station, a first radio network temporaryidentifier that is different from a second radio network temporaryidentifier of a second local manager node device in the cell. The firstradio network temporary identifier can be used for sidelinktransmissions of the local manager node device, the transmitter nodedevice and at least one receiver node device that is managed by themanager node device.

The local manager node device can comprise a first local manager nodedevice in a cell; aspects can comprise receiving, by the local managernode device from a base station, a radio network temporary identifierfor sidelink transmissions that is shared with second local manager nodedevice in the cell, wherein resource pools of the first local managernode device and the second local manager node device are orthogonal. Theradio network temporary identifier can be used for sidelinktransmissions of the local manager node device, the transmitter nodedevice and at least one receiver node device that is managed by themanager node device.

One or more example aspects are represented in FIG. 9, and cancorrespond to a transmitter node device 950, comprising a processor, anda memory that stores executable instructions that, when executed by theprocessor, facilitate performance of operations. Example operation 902represents receiving common downlink control information from a localmanager node device of a three-party wireless communication system,wherein the common downlink control information comprises schedulinginformation that schedules a data transmission from the transmitter nodedevice and identification information that identifies the transmitternode device of the three-party wireless communication system; Exampleoperation 904 represent transmitting data to a receiver node devicebased on the scheduling information.

Further operations can comprise determining that the common downlinkcontrol information was correctly received, and in response to thedetermining, acknowledging, by the transmitter node device to the localmanager node device, receiving the common downlink control information.

Receiving the common downlink control information can comprise utilizinga sidelink interface. Transmitting the data to the receiver node devicecan comprise utilizing a sidelink interface.

Further operations can comprise transmitting a scheduling request to thelocal manager node device, wherein receiving the common downlink controlinformation is in response to the scheduling request. The schedulingrequest can identify the receiver node device, and the common downlinkcontrol information further can identify the receiver node device. Thescheduling request can identify the receiver node device for a unicasttransmission, and the common downlink control information can identifythe transmitter node device in a transmitter unique identifier field andcan identify the receiver node device in a receiver unique identifierfield.

One or more aspects, such as implemented in a machine-readable storagemedium, comprising executable instructions that, when executed by aprocessor, facilitate performance of example operations, are representedin FIG. 10. Operation 1002 represents receiving a scheduling request atthe local manager node device from a transmitter node device managed bythe local manager node device, the scheduling request requestingscheduling of a data transmission to a receiver node device managed bythe local manager node device. Operation 1002 represents, in response tothe receiving the scheduling request, scheduling the data transmissionin common downlink control information that identifies the transmitternode device, and transmitting the common downlink control information tothe transmitter node device and the receiver node device.

Further operations can comprise broadcasting information that identifiesa group of nodes managed by the local manager node device. Furtheroperations can comprise receiving an acknowledgment from the transmitternode device in response to the transmitting the common downlink controlinformation. Further operations can comprise detecting the datatransmission from the transmitter node device as an implicitacknowledgement that the common downlink control information wassuccessfully received at the transmitter node device.

As can be seen, there is described herein a technology by which nodes ina three party communication system can communicate. A localmanager/scheduler node sends common downlink control information to atransmitting node and one or more receiving node(s) that schedules adata transmission, via sidelink, from the transmitting node to thereceiving node. The transmitting node can explicitly or implicitlyacknowledge reception of the downlink control information. Thetechnology facilitates unicast and broadcast/multicast datatransmissions. The transmitting node can request the scheduling of thedata transmission, e.g., identifying the receiving node for a unicastdata transmission.

A wireless communication system can employ various cellular systems,technologies, and modulation schemes to facilitate wireless radiocommunications between devices (e.g., a UE and the network device).While example embodiments might be described for 5G new radio (NR)systems, the embodiments can be applicable to any radio accesstechnology (RAT) or multi-RAT system where the UE operates usingmultiple carriers e.g. LTE FDD/TDD, GSM/GERAN, CDMA2000 etc. Forexample, the system can operate in accordance with global system formobile communications (GSM), universal mobile telecommunications service(UMTS), long term evolution (LTE), LTE frequency division duplexing (LTEFDD, LTE time division duplexing (TDD), high speed packet access (HSPA),code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000,time division multiple access (TDMA), frequency division multiple access(FDMA), multi-carrier code division multiple access (MC-CDMA),single-carrier code division multiple access (SC-CDMA), single-carrierFDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM),discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrierFDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM,resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However,various features and functionalities of system are particularlydescribed wherein the devices (e.g., the UEs and the network device) ofthe system are configured to communicate wireless signals using one ormore multi carrier modulation schemes, wherein data symbols can betransmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g. interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, the system can be configured to provide andemploy 5G wireless networking features and functionalities. With 5Gnetworks that may use waveforms that split the bandwidth into severalsub-bands, different types of services can be accommodated in differentsub-bands with the most suitable waveform and numerology, leading toimproved spectrum utilization for 5G networks. Notwithstanding, in themmWave spectrum, the millimeter waves have shorter wavelengths relativeto other communications waves, whereby mmWave signals can experiencesevere path loss, penetration loss, and fading. However, the shorterwavelength at mmWave frequencies also allows more antennas to be packedin the same physical dimension, which allows for large-scale spatialmultiplexing and highly directional beamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the third-generation partnershipproject (3GPP) and has been in use (including with LTE), is amulti-antenna technique that can improve the spectral efficiency oftransmissions, thereby significantly boosting the overall data carryingcapacity of wireless systems. The use of multiple-input multiple-output(MIMO) techniques can improve mmWave communications; MIMO can be usedfor achieving diversity gain, spatial multiplexing gain and beamforminggain.

Note that using multi-antennas does not always mean that MIMO is beingused. For example, a configuration can have two downlink antennas, andthese two antennas can be used in various ways. In addition to using theantennas in a 2×2 MIMO scheme, the two antennas can also be used in adiversity configuration rather than MIMO configuration. Even withmultiple antennas, a particular scheme might only use one of theantennas (e.g., LTE specification's transmission mode 1, which uses asingle transmission antenna and a single receive antenna). Or, only oneantenna can be used, with various different multiplexing, precodingmethods etc.

The MIMO technique uses a commonly known notation (M×N) to representMIMO configuration in terms number of transmit (M) and receive antennas(N) on one end of the transmission system. The common MIMOconfigurations used for various technologies are: (2×1), (1×2), (2×2),(4×2), (8×2) and (2×4), (4×4), (8×4). The configurations represented by(2×1) and (1×2) are special cases of MIMO known as transmit diversity(or spatial diversity) and receive diversity. In addition to transmitdiversity (or spatial diversity) and receive diversity, other techniquessuch as spatial multiplexing (comprising both open-loop andclosed-loop), beamforming, and codebook-based precoding can also be usedto address issues such as efficiency, interference, and range.

Referring now to FIG. 11, illustrated is a schematic block diagram of anexample end-user device such as a user equipment) that can be a mobiledevice 1100 capable of connecting to a network in accordance with someembodiments described herein. Although a mobile handset 1100 isillustrated herein, it will be understood that other devices can be amobile device, and that the mobile handset 1100 is merely illustrated toprovide context for the embodiments of the various embodiments describedherein. The following discussion is intended to provide a brief, generaldescription of an example of a suitable environment 1100 in which thevarious embodiments can be implemented. While the description includes ageneral context of computer-executable instructions embodied on amachine-readable storage medium, those skilled in the art will recognizethat the various embodiments also can be implemented in combination withother program modules and/or as a combination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The handset 1100 includes a processor 1102 for controlling andprocessing all onboard operations and functions. A memory 1104interfaces to the processor 1102 for storage of data and one or moreapplications 1106 (e.g., a video player software, user feedbackcomponent software, etc.). Other applications can include voicerecognition of predetermined voice commands that facilitate initiationof the user feedback signals. The applications 1106 can be stored in thememory 1104 and/or in a firmware 1108, and executed by the processor1102 from either or both the memory 1104 or/and the firmware 1108. Thefirmware 1108 can also store startup code for execution in initializingthe handset 1100. A communications component 1110 interfaces to theprocessor 1102 to facilitate wired/wireless communication with externalsystems, e.g., cellular networks, VoIP networks, and so on. Here, thecommunications component 1110 can also include a suitable cellulartransceiver 1111 (e.g., a GSM transceiver) and/or an unlicensedtransceiver 1113 (e.g., Wi-Fi, WiMax) for corresponding signalcommunications. The handset 1100 can be a device such as a cellulartelephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 1110 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The handset 1100 includes a display 1112 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1112 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1112 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1114 is provided in communication with the processor 1102 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 1100, for example. Audio capabilities areprovided with an audio I/O component 1116, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 1116 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 1100 can include a slot interface 1118 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 1120, and interfacingthe SIM card 1120 with the processor 1102. However, it is to beappreciated that the SIM card 1120 can be manufactured into the handset1100, and updated by downloading data and software.

The handset 1100 can process IP data traffic through the communicationcomponent 1110 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 800 and IP-based multimediacontent can be received in either an encoded or decoded format.

A video processing component 1122 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1122can aid in facilitating the generation, editing and sharing of videoquotes. The handset 1100 also includes a power source 1124 in the formof batteries and/or an AC power subsystem, which power source 1124 caninterface to an external power system or charging equipment (not shown)by a power I/O component 1126.

The handset 1100 can also include a video component 1130 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 1130 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1132 facilitates geographically locating the handset 1100. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 1134facilitates the user initiating the quality feedback signal. The userinput component 1134 can also facilitate the generation, editing andsharing of video quotes. The user input component 1134 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1106, a hysteresis component 1136facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1138 can be provided that facilitatestriggering of the hysteresis component 1138 when the Wi-Fi transceiver1113 detects the beacon of the access point. A SIP client 1140 enablesthe handset 1100 to support SIP protocols and register the subscriberwith the SIP registrar server. The applications 1106 can also include aclient 1142 that provides at least the capability of discovery, play andstore of multimedia content, for example, music.

The handset 1100, as indicated above related to the communicationscomponent 810, includes an indoor network radio transceiver 1113 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 1100. The handset 1100 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Referring now to FIG. 12, there is illustrated a block diagram of acomputer 1200 operable to execute the functions and operations performedin the described example embodiments. For example, a network node (e.g.,network node 126, GNB 202, etc.) may contain components as described inFIG. 12. The computer 1200 can provide networking and communicationcapabilities between a wired or wireless communication network and aserver and/or communication device. In order to provide additionalcontext for various aspects thereof, FIG. 1 and the following discussionare intended to provide a brief, general description of a suitablecomputing environment in which the various aspects of the embodimentscan be implemented to facilitate the establishment of a transactionbetween an entity and a third party. While the description above is inthe general context of computer-executable instructions that can run onone or more computers, those skilled in the art will recognize that thevarious embodiments also can be implemented in combination with otherprogram modules and/or as a combination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the various embodiments can also be practicedin distributed computing environments where certain tasks are performedby remote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 12, implementing various aspects described hereinwith regards to the end-user device can include a computer 1200, thecomputer 1200 including a processing unit 1204, a system memory 1206 anda system bus 1208. The system bus 1208 couples system componentsincluding, but not limited to, the system memory 1206 to the processingunit 1204. The processing unit 1204 can be any of various commerciallyavailable processors. Dual microprocessors and other multi-processorarchitectures can also be employed as the processing unit 1204.

The system bus 1208 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1206includes read-only memory (ROM) 1227 and random access memory (RAM)1212. A basic input/output system (BIOS) is stored in a non-volatilememory 1227 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1200, such as during start-up. The RAM 1212 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1200 further includes an internal hard disk drive (HDD)1214 (e.g., EIDE, SATA), which internal hard disk drive 1214 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1216, (e.g., to read from or write to aremovable diskette 1218) and an optical disk drive 1220, (e.g., readinga CD-ROM disk 1222 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1214, magnetic diskdrive 1216 and optical disk drive 1220 can be connected to the systembus 1208 by a hard disk drive interface 1224, a magnetic disk driveinterface 1226 and an optical drive interface 1228, respectively. Theinterface 1224 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1394 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject embodiments.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1200 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 1200, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the example operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed embodiments.

A number of program modules can be stored in the drives and RAM 1212,including an operating system 1230, one or more application programs1232, other program modules 1234 and program data 1236. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1212. It is to be appreciated that the variousembodiments can be implemented with various commercially availableoperating systems or combinations of operating systems.

A user can enter commands and information into the computer 1200 throughone or more wired/wireless input devices, e.g., a keyboard 1238 and apointing device, such as a mouse 1240. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1204 through an input deviceinterface 1242 that is coupled to the system bus 1208, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1244 or other type of display device is also connected to thesystem bus 1208 through an interface, such as a video adapter 1246. Inaddition to the monitor 1244, a computer 1200 typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1200 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1248. The remotecomputer(s) 1248 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer,although, for purposes of brevity, only a memory/storage device 1250 isillustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 1252 and/or larger networks,e.g., a wide area network (WAN) 1254. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1200 isconnected to the local network 1252 through a wired and/or wirelesscommunication network interface or adapter 1256. The adapter 1256 mayfacilitate wired or wireless communication to the LAN 1252, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1256.

When used in a WAN networking environment, the computer 1200 can includea modem 1258, or is connected to a communications server on the WAN1254, or has other means for establishing communications over the WAN1254, such as by way of the Internet. The modem 1258, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1208 through the input device interface 1242. In a networkedenvironment, program modules depicted relative to the computer, orportions thereof, can be stored in the remote memory/storage device1250. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE802.11 (a, b,g, n, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE802.3 or Ethernet). Wi-Finetworks operate in the unlicensed 2.4 and 8 GHz radio bands, at an 12Mbps (802.11b) or 84 Mbps (802.11a) data rate, for example, or withproducts that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic “10BaseT” wiredEthernet networks used in many offices.

As it employed in the subject specification, the term “processor” canrefer to substantially any computing processing unit or devicecomprising, but not limited to comprising, single-core processors;single-processors with software multithread execution capability;multi-core processors; multi-core processors with software multithreadexecution capability; multi-core processors with hardware multithreadtechnology; parallel platforms; and parallel platforms with distributedshared memory. Additionally, a processor can refer to an integratedcircuit, an application specific integrated circuit (ASIC), a digitalsignal processor (DSP), a field programmable gate array (FPGA), aprogrammable logic controller (PLC), a complex programmable logic device(CPLD), a discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. Processors can exploit nano-scale architectures suchas, but not limited to, molecular and quantum-dot based transistors,switches and gates, in order to optimize space usage or enhanceperformance of user equipment. A processor also can be implemented as acombination of computing processing units.

In the subject specification, terms such as “store,” “data store,” “datastorage,” “database,” “repository,” “queue”, and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can comprise both volatile andnonvolatile memory. In addition, memory components or memory elementscan be removable or stationary. Moreover, memory can be internal orexternal to a device or component, or removable or stationary. Memorycan comprise various types of media that are readable by a computer,such as hard-disc drives, zip drives, magnetic cassettes, flash memorycards or other types of memory cards, cartridges, or the like.

By way of illustration, and not limitation, nonvolatile memory cancomprise read only memory (ROM), programmable ROM (PROM), electricallyprogrammable ROM (EPROM), electrically erasable ROM (EEPROM), or flashmemory. Volatile memory can comprise random access memory (RAM), whichacts as external cache memory. By way of illustration and notlimitation, RAM is available in many forms such as synchronous RAM(SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rateSDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), anddirect Rambus RAM (DRRAM). Additionally, the disclosed memory componentsof systems or methods herein are intended to comprise, without beinglimited to comprising, these and any other suitable types of memory.

In particular and in regard to the various functions performed by theabove described components, devices, circuits, systems and the like, theterms (including a reference to a “means”) used to describe suchcomponents are intended to correspond, unless otherwise indicated, toany component which performs the specified function of the describedcomponent (e.g., a functional equivalent), even though not structurallyequivalent to the disclosed structure, which performs the function inthe herein illustrated example aspects of the embodiments. In thisregard, it will also be recognized that the embodiments comprise asystem as well as a computer-readable medium having computer-executableinstructions for performing the acts and/or events of the variousmethods.

Computing devices typically comprise a variety of media, which cancomprise computer-readable storage media and/or communications media,which two terms are used herein differently from one another as follows.Computer-readable storage media can be any available storage media thatcan be accessed by the computer and comprises both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, solid state drive (SSD) or other solid-state storagetechnology, compact disk read only memory (CD ROM), digital versatiledisk (DVD), Blu-ray disc or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices or other tangible and/or non-transitory media which canbe used to store desired information.

In this regard, the terms “tangible” or “non-transitory” herein asapplied to storage, memory or computer-readable media, are to beunderstood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se. Computer-readable storage media can be accessed by oneor more local or remote computing devices, e.g., via access requests,queries or other data retrieval protocols, for a variety of operationswith respect to the information stored by the medium.

On the other hand, communications media typically embodycomputer-readable instructions, data structures, program modules orother structured or unstructured data in a data signal such as amodulated data signal, e.g., a carrier wave or other transportmechanism, and comprises any information delivery or transport media.The term “modulated data signal” or signals refers to a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in one or more signals. By way of example, and notlimitation, communications media comprise wired media, such as a wirednetwork or direct-wired connection, and wireless media such as acoustic,RF, infrared and other wireless media

Further, terms like “user equipment,” “user device,” “mobile device,”“mobile,” station,” “access terminal,” “terminal,” “handset,” andsimilar terminology, generally refer to a wireless device utilized by asubscriber or user of a wireless communication network or service toreceive or convey data, control, voice, video, sound, gaming, orsubstantially any data-stream or signalling-stream. The foregoing termsare utilized interchangeably in the subject specification and relateddrawings. Likewise, the terms “access point,” “node B,” “base station,”“evolved Node B,” “cell,” “cell site,” and the like, can be utilizedinterchangeably in the subject application, and refer to a wirelessnetwork component or appliance that serves and receives data, control,voice, video, sound, gaming, or substantially any data-stream orsignalling-stream from a set of subscriber stations. Data and signallingstreams can be packetized or frame-based flows. It is noted that in thesubject specification and drawings, context or explicit distinctionprovides differentiation with respect to access points or base stationsthat serve and receive data from a mobile device in an outdoorenvironment, and access points or base stations that operate in aconfined, primarily indoor environment overlaid in an outdoor coveragearea. Data and signalling streams can be packetized or frame-basedflows.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,” andthe like are employed interchangeably throughout the subjectspecification, unless context warrants particular distinction(s) amongthe terms. It should be appreciated that such terms can refer to humanentities, associated devices, or automated components supported throughartificial intelligence (e.g., a capacity to make inference based oncomplex mathematical formalisms) which can provide simulated vision,sound recognition and so forth. In addition, the terms “wirelessnetwork” and “network” are used interchangeable in the subjectapplication, when context wherein the term is utilized warrantsdistinction for clarity purposes such distinction is made explicit.

Moreover, the word “exemplary” is used herein to mean serving as anexample, instance, or illustration. Any aspect or design describedherein as “exemplary” is not necessarily to be construed as preferred oradvantageous over other aspects or designs. Rather, use of the wordexemplary is intended to present concepts in a concrete fashion. As usedin this application, the term “or” is intended to mean an inclusive “or”rather than an exclusive “or”. That is, unless specified otherwise, orclear from context, “X employs A or B” is intended to mean any of thenatural inclusive permutations. That is, if X employs A; X employs B; orX employs both A and B, then “X employs A or B” is satisfied under anyof the foregoing instances. In addition, the articles “a” and “an” asused in this application and the appended claims should generally beconstrued to mean “one or more” unless specified otherwise or clear fromcontext to be directed to a singular form.

In addition, while a particular feature may have been disclosed withrespect to only one of several implementations, such feature may becombined with one or more other features of the other implementations asmay be desired and advantageous for any given or particular application.Furthermore, to the extent that the terms “includes” and “including” andvariants thereof are used in either the detailed description or theclaims, these terms are intended to be inclusive in a manner similar tothe term “comprising.”

The above descriptions of various embodiments of the subject disclosureand corresponding figures and what is described in the Abstract, aredescribed herein for illustrative purposes, and are not intended to beexhaustive or to limit the disclosed embodiments to the precise formsdisclosed. It is to be understood that one of ordinary skill in the artmay recognize that other embodiments having modifications, permutations,combinations, and additions can be implemented for performing the same,similar, alternative, or substitute functions of the disclosed subjectmatter, and are therefore considered within the scope of thisdisclosure. Therefore, the disclosed subject matter should not belimited to any single embodiment described herein, but rather should beconstrued in breadth and scope in accordance with the claims below.

What is claimed is:
 1. A method, comprising: determining, by a localmanager user equipment comprising a processor, that common downlinkcontrol information was not correctly received by a transmitter userequipment; and retransmitting, by the local manager user equipment tothe transmitter user equipment and a receiver user equipment,corresponding common downlink control information, wherein thecorresponding common downlink control information identifies thetransmitter user equipment and reschedules an associated datatransmission by the transmitter user equipment to the receiver userequipment.
 2. The method of claim 1, further comprising receiving, bythe local manager user equipment, an explicit acknowledgment from thetransmitter user equipment indicating that the corresponding commondownlink control information was successfully received by thetransmitter user equipment, and wherein determining that the commondownlink control information was correctly received by the transmitteruser equipment is based on the explicit acknowledgment.
 3. The method ofclaim 1, further comprising detecting, by the local manager userequipment, a data transmission from the transmitter user equipment thatcorresponds to the corresponding common downlink control information,and using the detecting as an implicit acknowledgment that thecorresponding common downlink control information was correctly receivedby the transmitter user equipment.
 4. The method of claim 1, furthercomprising adding, by the local manager user equipment, a uniquetransmitter identifier that represents the transmitter user equipment toa unique transmitter identifier field in the corresponding commondownlink control information.
 5. The method of claim 1, wherein theassociated data transmission comprises a unicast data transmission, andfurther comprising configuring, by the local manager user equipment, thecorresponding common downlink control information to identify thereceiver user equipment.
 6. The method of claim 5, wherein configuringthe corresponding common downlink control information comprises adding aunique transmitter identifier that represents the transmitter userequipment to a unique transmitter identifier field and adding a uniquereceiver identifier that represents the receiver user equipment to aunique receiver identifier field in the corresponding common downlinkcontrol information.
 7. The method of claim 1, further comprisingreceiving, by the local manager user equipment, a scheduling requestfrom the transmitter user equipment.
 8. A local manager device,comprising: a processor; and a memory that stores executableinstructions that, when executed by the processor, facilitateperformance of operations, comprising: determining that common downlinkcontrol information was not correctly received by a transmitter device;and retransmitting corresponding common downlink control information tothe transmitter device and a receiver device, wherein the correspondingcommon downlink control information identifies the transmitter deviceand reschedules an associated data transmission by the transmitterdevice to the receiver device.
 9. The local manager device of claim 8,wherein the operations further comprise receiving an explicitacknowledgment from the transmitter device indicating that thecorresponding common downlink control information was successfullyreceived by the transmitter device, and wherein determining that thecommon downlink control information was correctly received by thetransmitter device is based on the explicit acknowledgment.
 10. Thelocal manager device of claim 8, wherein the operations further comprisedetecting a data transmission from the transmitter device thatcorresponds to the corresponding common downlink control information,and using a result of the detecting as an implicit acknowledgment thatthe corresponding common downlink control information was correctlyreceived by the transmitter device.
 11. The local manager device ofclaim 8, wherein the operations further comprise adding a uniquetransmitter identifier that represents the transmitter device to aunique transmitter identifier field in the corresponding common downlinkcontrol information.
 12. The local manager device of claim 8, whereinthe associated data transmission comprises a unicast data transmission,and further comprising configuring the corresponding common downlinkcontrol information to identify the receiver device.
 13. The localmanager device of claim 12, wherein configuring the corresponding commondownlink control information comprises adding a unique transmitteridentifier that represents the transmitter device to a uniquetransmitter identifier field and adding a unique receiver identifierthat represents the receiver device to a unique receiver identifierfield in the corresponding common downlink control information.
 14. Thelocal manager device of claim 8, wherein the operations further comprisereceiving a scheduling request from the transmitter device.
 15. Anon-transitory machine-readable medium, comprising executableinstructions that, when executed by a processor of a local manager node,facilitate performance of operations, comprising: determining thatcommon downlink control information was not correctly received by atransmitter node; and retransmitting corresponding common downlinkcontrol information to the transmitter node and a receiver node, whereinthe corresponding common downlink control information identifies thetransmitter node and reschedules an associated data transmission by thetransmitter node to the receiver node.
 16. The non-transitorymachine-readable medium of claim 15, wherein the operations furthercomprise receiving an explicit acknowledgment from the transmitter nodeindicating that the corresponding common downlink control informationwas successfully received by the transmitter node, and whereindetermining that the common downlink control information was correctlyreceived by the transmitter node is based on the explicitacknowledgment.
 17. The non-transitory machine-readable medium of claim15, wherein the operations further comprise detecting a datatransmission from the transmitter node that corresponds to thecorresponding common downlink control information, and, based on thedetecting, inferring that the corresponding common downlink controlinformation was correctly received by the transmitter node.
 18. Thenon-transitory machine-readable medium of claim 15, wherein theoperations further comprise adding a unique transmitter identifier thatrepresents the transmitter node to a unique transmitter identifier fieldin the corresponding common downlink control information.
 19. Thenon-transitory machine-readable medium of claim 15, wherein theassociated data transmission comprises a unicast data transmission, andfurther comprising configuring the corresponding common downlink controlinformation to identify the receiver node.
 20. The non-transitorymachine-readable medium of claim 19, wherein configuring thecorresponding common downlink control information comprises adding aunique transmitter identifier that represents the transmitter node to aunique transmitter identifier field and adding a unique receiveridentifier that represents the receiver node to a unique receiveridentifier field in the corresponding common downlink controlinformation.